Uplink ACK resource allocation in new radio

ABSTRACT

A method and apparatus for enabling an UE to selecting acknowledgement/non-acknowledgement (ACK/NACK) resources from a subset of a gNB resource pool. The example method may receive, from an gNB, a radio resource control (RRC) configuration indicating a UE-specific resource set that is a subset of a gNB resource pool. The UE may determine one or more ACK/NACK resources from the UE-specific resource set for an upcoming physical uplink control channel (PUCCH). In some aspects, the UE may determine the one or more ACK/NACK resources based on receiving, from the gNB, a physical downlink control channel (PDCCH) including a corresponding ACK/NACK resource configuration. In other aspects, the RRC may contain multiple resource subsets and the UE may determine the one or more ACK/NACK resources based on determining a size of a payload for a UCI to be transmitted on the PUCCH. The aspects may thus enable dynamic ACK/NACK resource allocation.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present Application for Patent claims priority to ProvisionalApplication No. 62/470,784 entitled “Uplink ACK Resource Allocation inNew Radio” filed Mar. 13, 2017, which is assigned to the assignee, andincorporated herein by reference in its entirety.

BACKGROUND

Aspects of the present disclosure relate generally to wirelesscommunication networks, and more particularly, to allocating ACK/NACKresources in wireless communications.

Wireless communication networks are widely deployed to provide varioustypes of communication content such as voice, video, packet data,messaging, broadcast, and so on. These systems may be multiple-accesssystems capable of supporting communication with multiple users bysharing the available system resources (e.g., time, frequency, andpower). Examples of such multiple-access systems include code-divisionmultiple access (CDMA) systems, time-division multiple access (TDMA)systems, frequency-division multiple access (FDMA) systems, orthogonalfrequency-division multiple access (OFDMA) systems, and single-carrierfrequency division multiple access (SC-FDMA) systems.

These multiple access technologies have been adopted in varioustelecommunication standards to provide a common protocol that enablesdifferent wireless devices to communicate on a municipal, national,regional, and even global level. For example, a fifth generation (5G)wireless communications technology (which can be referred to as newradio (NR)) is envisaged to expand and support diverse usage scenariosand applications with respect to current mobile network generations. Inan aspect, 5G communications technology can include: enhanced mobilebroadband addressing human-centric use cases for access to multimediacontent, services and data; ultra-reliable-low latency communications(URLLC) with certain specifications for latency and reliability; andmassive machine type communications, which can allow a very large numberof connected devices and transmission of a relatively low volume ofnon-delay-sensitive information. As the demand for mobile broadbandaccess continues to increase, however, further improvements in NRcommunications technology and beyond may be desired.

For example, in a new radio (NR), multiple downlink (DL)/uplink (UL)sub-bands may be configured for allocating acknowledgement(ACK)/negativeacknowledgement (NACK) resources (e.g., ACK/NACK resources). However,the mapping between DL and UL sub-bands is not limited to one-to-onemapping and there may be cross-slot scheduling as well. Thus,improvements to efficiently allocate ACK resources in wirelesscommunications may be desired.

SUMMARY OF THE INVENTION

The following presents a simplified summary of one or more aspects toprovide a basic understanding of such aspects. This summary is not anextensive overview of all contemplated aspects, and is intended toneither identify key or critical elements of all aspects nor delineateany aspects. Its sole purpose is to present concepts of one or moreaspects in a simplified form as a prelude to the more detaileddescription presented later.

In an aspect, the present disclosure includes a method for wirelesscommunications. The example method may receive, from an gNB, a radioresource control (RRC) configuration indicating a UE-specific resourceset that is a subset of a gNB resource pool. The method may alsoreceive, from the gNB, a physical downlink control channel (PDCCH)including a corresponding ACK/NACK resource configuration. Further, theexample method may determine one or moreacknowledgement/non-acknowledgement (ACK/NACK) resources from theUE-specific resource set for an upcoming physical uplink control channel(PUCCH) based, at least in part, on the ACK/NACK resource configuration.

The present disclosure also includes an apparatus having componentsconfigured to execute or means for executing the above-described method,and a computer-readable medium storing one or more codes executable by aprocessor to perform the above-described method.

Further aspects of the present disclosure may include another method forwireless communications. The example method may receive, from a gNB, aradio resource channel (RRC) configuration indicating multipleUE-specific uplink control information (UCI) resource sets that aresubsets of a gNB resource pool. The method may also determine a size ofa payload for a UCI to be transmitted on a physical uplink controlchannel (PUCCH). Further, the example method may determine a selectedUE-specific UCI resource set from the multiple UE-specific resource setsfor transmitting the UCI on the PUCCH based, at least in part, on thesize of the payload of the UCI.

In some aspects, the example method may further include receiving, fromthe gNB, a physical downlink control channel (PDCCH) including acorresponding acknowledgement (ACK)/non-acknowledgement (NACK) resourceconfiguration. The determination of the selected UE-specific UCIresource set may further include determining based, at least in part, onthe ACK/NACK resource configuration.

Further aspects of the method may include identifying a payload sizerange for each of the multiple UE-specific resource sets. The method mayinclude identifying which of the payload size ranges include the size ofthe payload for the UCI. The payload size range corresponding to themultiple resource sets may be indicated in the RRC configuration.Further, the method may include selecting the selected UE-specific UCIresource set from one the multiple UE-specific resource sets identifiedas having a corresponding payload size range that includes the size ofthe payload of the UCI.

In a further aspect, the present disclosure includes a method ofwireless communications at a gNB. The gNB may include a transceiver, amemory, and a processor coupled to the transceiver and memory, whereinthe processor is configured to perform the method. The method includestransmitting, to a UE, a radio resource control (RRC) configurationindicating a UE-specific resource set that is a subset of a gNB resourcepool. The method further includes transmitting, to the UE, a physicaldownlink control channel (PDCCH) including a corresponding ACK/NACKresource configuration. The method further includes transmitting, to theUE, user data on a physical downlink shared channel (PDSCH). The methodfurther includes receiving, from the UE, an ACK/NACK for the user datatransmitted on the PDSCH on at least one ACK/NACK resource determined,by the UE, based at least in part on the ACK/NACK resourceconfiguration.

The present disclosure also includes a gNB apparatus having components(e.g., a processor) configured to execute or means for executing theabove-described method, and a computer-readable medium storing one ormore codes executable by a processor to perform the above-describedmethod.

In a further aspect, the present disclosure includes a method ofwireless communications at a gNB. The gNB may include a transceiver, amemory, and a processor coupled to the transceiver and memory. Themethod includes transmitting, to a UE, a radio resource channel (RRC)configuration indicating multiple UE-specific uplink control information(UCI) resource sets that are subsets of a gNB resource pool. The methodfurther includes receiving, from the UE, a UCI in a UE-specific UCIresource set selected by the UE based on a payload size of the UCI.

The present disclosure also includes a gNB apparatus having components(e.g., a processor) configured to execute or means for executing theabove-described method, and a computer-readable medium storing one ormore codes executable by a processor to perform the above-describedmethod.

To the accomplishment of the foregoing and related ends, the one or moreaspects comprise the features described and particularly pointed out inthe claims. This description and the annexed drawings set forth indetail certain illustrative features of the one or more aspects. Thesefeatures are indicative, however, of but a few of the ways in which theprinciples of various aspects may be employed, and this descriptionshould include all such aspects and their equivalents.

BRIEF DESCRIPTION OF THE DRAWINGS

The disclosed aspects will hereinafter be described in conjunction withthe appended drawings, provided to illustrate and not to limit thedisclosed aspects, wherein like designations denote like elements, andin which:

FIG. 1 is a schematic diagram of a wireless communication networkincluding at least one UE having a communications component configuredaccording to this disclosure to determine ACK/NACK resources, and atleast one base station having a corresponding communication componentconfigured according to this disclosure.

FIGS. 2A and 2B are schematic diagrams of example ACK resourceallocations respectively for PUCCH formats 1a and 1b.

FIG. 3A is a schematic diagram of an example sub-band dependent mappingaccording to an aspect of the present disclosure.

FIG. 3B is a schematic diagram of an additional example sub-banddependent mapping according to an aspect of the present disclosure.

FIG. 4A is a schematic diagram of an example cross-slot schedulingconfiguration according to an aspect of the present disclosure.

FIG. 4B is a schematic diagram of an additional example cross-slotscheduling configuration according to an aspect of the presentdisclosure.

FIG. 5 is a schematic diagram of an example of a variable ACK format 500according to aspects of the present disclosure.

FIG. 6 is a flow diagram of an example method of wireless communicationincluding determining ACK/NACK resources at a user equipment accordingto an aspect of the present disclosure.

FIG. 7 is a flow diagram of an example method of wireless communicationincluding determining ACK/NACK resources from multiple uplink controlinformation (UCI) resource sets at a user equipment according to anaspect of the present disclosure.

FIG. 8 is a flow diagram of an example method of wireless communicationincluding determining ACK/NACK resources at a gNB according to an aspectof the present disclosure.

FIG. 9 is a flow diagram of an example method of wireless communicationincluding determining ACK/NACK resources from multiple uplink controlinformation (UCI) resource sets at a gNB according to an aspect of thepresent disclosure.

FIG. 10 is a schematic diagram of example components of the UE of FIG.1.

FIG. 11 is a schematic diagram of example components of the base stationof FIG. 1.

DETAILED DESCRIPTION

Various aspects are now described with reference to the drawings. In thefollowing description, for purposes of explanation, numerous specificdetails are set forth in order to provide a thorough understanding ofone or more aspects. It may be evident, however, that such aspect(s) maybe practiced without these specific details. Additionally, the term“component” as used herein may be one of the parts that make up asystem, may be hardware, firmware, and/or software stored on acomputer-readable medium, and may be divided into other components.

The present disclosure provides aspects that enable a UE to identifyuplink control information (UCI) resources within a UE-specific resourceset based on an indication received from a gNB, combined with implicitand/or explicit mapping, and/or based on a payload size of a UCI to betransmitted. In these cases, the UE-specific resource set may be asubset of a gNB resource pool, and may be pooled into multiple differentsets of physical resources (e.g., multiple different UE-specificresource sets).

For example, in one implementation of identifying one or more UCIresources within a UE-specific resource set, a UE may receive a radioresource control (RRC) configuration that is transmitted by a gNB andthat indicates the UE-specific resource set. Further, the UE may receivea physical downlink control channel (PDCCH) that includes acorresponding acknowledgement (ACK)/non-acknowledgement (NACK) resourceconfiguration. The ACK/NACK resource configuration (e.g., configurationinformation) may indicate to the UE which UCI resource(s) (e.g.,ACK/NACK resource(s)) from the UE-specific resource set are to be usedby the UE for transmitting ACK/NACKs on physical uplink control channels(PUCCHs) to the gNB. For instance, in some non-limiting cases, theACK/NACK resource configuration includes an acknowledgement resourceindicator (ARI), and the UE determines which resource(s) from theUE-specific resource set to use based on a value of the ARI.Alternatively or additionally, for instance, in some other non-limitingcases, the UE determines which resource(s) from the UE-specific resourceset to use based on an implicit mapping method. In some case, the UE maydetermine which resource(s) from a location of a control channel element(CCE) carrying the ACK/NACK resource configuration. Alternatively oradditionally, for instance, in yet other non-limiting cases, the UEdetermines which resource(s) from the UE-specific resource set to usebased on an explicit mapping with some DCI bits other than ARI bits. Forexample, some invalid DCI bits may be used to indicate one of theresource in the resource set. Alternatively or additionally, forinstance, in yet other non-limiting cases, the UE determines whichresource(s) from the UE-specific resource set to use based on at leastone of downlink(DL)/uplink (UL) sub-band mapping information, cross-slotscheduling information, or a format of the ACK/NACK resourceconfiguration. Upon determining the UCI or ACK/NACK resource(s) to usefrom the UE-specific resource set, the UE may transmit ACK/NACKs to thegNB using the determined ACK/NACK resource(s).

Additionally, for example, in another implementation of identifying UCIresources within a UE-specific resource set, the UE may determine a sizeof a payload for a UCI to be transmitted on a PUCCH. Then, the UE mayidentify a selected UE-specific UCI resource set from the multipleUE-specific resource sets for transmitting the UCI on the PUCCH based,at least in part, on the size of the payload of the UCI. For example,the UE may determine the selected UE-specific UCI resource set from themultiple UE-specific resource sets based on a mapping of differentpayload size ranges to respective ones of the multiple UE-specificresource sets.

The present solutions may address one or more issues with pre-New Radio(NR)/5G LTE technologies, which employed implicit mapping techniques forACK/NACK configuration in a PDCCH. However, such techniques may not befully suitable for NR/5G operations. For example, an LTE eNB may be acarrier aggregated cell with one primary cell and one or more secondarycells. LTE eNBs may use implicit mapping to allocate (e.g., assign,identify, etc.) ACK/NACK resources for a primary cell and explicitselection with ACK/NACK resource indicator (ARI) to allocate ACK/NACKresources for a secondary cell. Further, for example, an ACK/NACKresource may be a time/frequency resource which may identify afrequency, shift, code division multiplexing (CDM), etc., associatedwith the specific ACK resource. The LTE techniques do not account forthe existence of multiple DL/UL sub-bands in NR/5G, however, leading tocollisions across carriers.

In NR, multiple DL/UL sub-bands may be configured and the DL sub-bandsand the UL sub-bands may have one-to-one mapping or a many-to-onemapping (more than one DL sub-band mapped to one UL sub-band). Ifmultiple DL sub-bands are mapped to one UL sub-band, the techniquesutilized in LTE are not suitable and, as addressed herein, the ACKresources may be assigned/allocated in a way to minimize and/or avoidresource collisions. In other words, the ACK resource is generally notassigned to multiple PUCCHs of different UEs.

The various aspects described in this disclosure provide multipletechniques for mapping ACK/NACK resources within a UE-specific resourceset for use by the UE based on configuration information indicated bythe PDCCH, using a combination of implicit and explicit rules, and/orbased on a payload size of a UCI to be transmitted. By defining mappingschemes for use by the UE and gNB to identify one or more resourceswithin the UE-specific resource set that may be used to transmit anACK/NACK during a PUCCH, the present disclosure reduces the likelihoodof collisions between ACK/NACK transmissions of multiple UEs. Thevarious aspects thus provide a technical improvement in the art oftelecommunications and specifically NR, by reducing the likelihood ofACK/NACK collision and the resultant failed receipt of the ACK or NACK.

Additional features of the present aspects are described in more detailbelow with respect to FIGS. 1-9.

It should be noted that the techniques described herein may be used forvarious wireless communication networks such as CDMA, TDMA, FDMA, OFDMA,SC-FDMA, and other systems. The terms “system” and “network” are oftenused interchangeably. A CDMA system may implement a radio technologysuch as CDMA2000, Universal Terrestrial Radio Access (UTRA), etc.CDMA2000 covers IS-2000, IS-95, and IS-856 standards. IS-2000 Releases 0and A are commonly referred to as CDMA2000 1×, 1×, etc. IS-856 (TIA-856)is commonly referred to as CDMA2000 1×EV-DO, High Rate Packet Data(HRPD), etc. UTRA includes Wideband CDMA (WCDMA) and other variants ofCDMA. A TDMA system may implement a radio technology such as GlobalSystem for Mobile Communications (GSM). An OFDMA system may implement aradio technology such as Ultra Mobile Broadband (UMB), Evolved UTRA(E-UTRA), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20,Flash-OFDM™, etc. UTRA and E-UTRA are part of Universal MobileTelecommunication System (UMTS). 3GPP Long Term Evolution (LTE) andLTE-Advanced (LTE-A) are new releases of UMTS that use E-UTRA. UTRA,E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents from anorganization named “3rd Generation Partnership Project” (3GPP). CDMA2000and UMB are described in documents from an organization named “3rdGeneration Partnership Project2” (3GPP2). The techniques describedherein may be used for the systems and radio technologies mentionedabove as well as other systems and radio technologies, includingcellular (e.g., LTE) communications over a shared radio frequencyspectrum band. The description below, however, describes an LTE/LTE-Asystem for purposes of example, and LTE terminology is used in much ofthe description below, although the techniques are applicable beyondLTE/LTE-A applications (e.g., to 5G networks or other next generationcommunication systems).

The following description provides examples, and is not limiting of thescope, applicability, or examples set forth in the claims. Changes maybe made in the function and arrangement of elements discussed withoutdeparting from the scope of the disclosure. Various examples may omit,substitute, or add various procedures or components as appropriate. Forinstance, the methods described may be performed in an order differentfrom that described, and various steps may be added, omitted, orcombined. Also, features described with respect to some examples may becombined in other examples.

Referring to FIG. 1, in accordance with various aspects of the presentdisclosure, an example wireless communication network 100 includes atleast user equipment (UE) 110 with a modem 140 having a communicationscomponent 150 that manages execution of a radio resource control(RRC)/physical downlink control channel (PDCCH) receiving component 152,an ACK/NACK resource determining component 154, and/or an ACK/NACKtransmitting component 156. The example wireless communication network100 may further include an gNB or a base station 105 with a modem 180having a communications component 190 that manages execution of a PDCCHtransmitting component 192 and/or an ACK/NACK receiving component 194 toreceive ACK/NACKs from the UE 110.

According to the present disclosure, for example, the gNB 105 maytransmit one or more PDCCHs to the UE 110. The PDCCHs may includeACK/NACK resource configuration (e.g., configuration information) whichmay indicate to the UE 110 the ACK/NACK resources to be used by the UE110 for transmitting ACK/NACKs on physical uplink control channel(PUCCH) to the gNB 105. For each PDCCH received from the gNB 105, the UE110 may determine the ACK/NACK resources based at least on a payloadand/or a location of the PDCCH. The payload and/or the location of thePDCCH may contain at least one of a DL/UL sub-band mapping information,cross-slot scheduling information, ACK formats, and/or ARIs. Upondetermining the ACK/NACK resources, the UE 110 may transmit ACK/NACKs tothe gNB 105 using the determined ACK/NACK resources.

The wireless communication network 100 may include one or more basestations 105, one or more UEs 110, and a core network 115. The corenetwork 115 may provide user authentication, access authorization,tracking, internet protocol (IP) connectivity, and other access,routing, or mobility functions. The base stations 105 may interface withthe core network 115 through backhaul links 120 (e.g., S1, etc.). Thebase stations 105 may perform radio configuration and scheduling forcommunication with the UEs 110, or may operate under the control of abase station controller (not shown). In various examples, the basestations 105 may communicate, either directly or indirectly (e.g.,through core network 115), with one another over backhaul links 125(e.g., X1, etc.), which may be wired or wireless communication links.

The base stations 105 may wirelessly communicate with the UEs 110 viaone or more base station antennas. Each of the base stations 105 mayprovide communication coverage for a respective geographic coverage area130. In some examples, base stations 105 may be referred to as a basetransceiver station, a radio base station, an access point, an accessnode, a radio transceiver, a NodeB, eNodeB (eNB), gNB, Home NodeB, aHome eNodeB, a relay, or some other suitable terminology. The geographiccoverage area 130 for a base station 105 may be divided into sectors orcells making up only a portion of the coverage area (not shown). Thewireless communication network 100 may include base stations 105 ofdifferent types (e.g., macro base stations or small cell base stations,described below). Additionally, the plurality of base stations 105 mayoperate according to different ones of a plurality of communicationtechnologies (e.g., 5G (New Radio or “NR”), fourth generation (4G)/LTE,3G, Wi-Fi, Bluetooth, etc.), and thus there may be overlappinggeographic coverage areas 130 for different communication technologies.

In some examples, the wireless communication network 100 may be orinclude one or any combination of communication technologies, includinga NR or 5G technology, a Long Term Evolution (LTE) or LTE-Advanced(LTE-A) or MuLTEfire technology, a Wi-Fi technology, a Bluetoothtechnology, or any other long or short range wireless communicationtechnology. In LTE/LTE-A/MuLTEfire networks, the term evolved node B(gNB) may be generally used to describe the base stations 105, while theterm UE may be generally used to describe the UEs 110. The wirelesscommunication network 100 may be a heterogeneous technology network inwhich different types of gNBs provide coverage for various geographicalregions. For example, each gNB or base station 105 may providecommunication coverage for a macro cell, a small cell, or other types ofcell. The term “cell” is a 3GPP term that can be used to describe a basestation, a carrier or component carrier associated with a base station,or a coverage area (e.g., sector, etc.) of a carrier or base station,depending on context.

A macro cell may generally cover a relatively large geographic area(e.g., several kilometers in radius) and may allow unrestricted accessby the UEs 110 with service subscriptions with the network provider.

A small cell may include a relative lower transmit-powered base station,as compared with a macro cell, that may operate in the same or differentfrequency bands (e.g., licensed, unlicensed, etc.) as macro cells. Smallcells may include pico cells, femto cells, and micro cells according tovarious examples. A pico cell, for example, may cover a small geographicarea and may allow unrestricted access by the UEs 110 with servicesubscriptions with the network provider. A femto cell may also cover asmall geographic area (e.g., a home) and may provide restricted accessand/or unrestricted access by the UEs 110 having an association with thefemto cell (e.g., in the restricted access case, the UEs 110 in a closedsubscriber group (CSG) of the base station 105, which may include theUEs 110 for users in the home, and the like). An gNB for a macro cellmay be referred to as a macro gNB. An gNB for a small cell may bereferred to as a small cell gNB, a pico gNB, a femto gNB, or a home gNB.An gNB may support one or multiple (e.g., two, three, four, and thelike) cells (e.g., component carriers).

The communication networks that may accommodate some of the variousdisclosed examples may be packet-based networks that operate accordingto a layered protocol stack and data in the user plane may be based onthe IP. A user plane protocol stack (e.g., packet data convergenceprotocol (PDCP), radio link control (RLC), MAC, etc.), may performpacket segmentation and reassembly to communicate over logical channels.For example, a MAC layer may perform priority handling and multiplexingof logical channels into transport channels. The MAC layer may also usehybrid automatic repeat/request (HARQ) to provide retransmission at theMAC layer to improve link efficiency. In the control plane, the RRCprotocol layer may provide establishment, configuration, and maintenanceof an RRC connection between a UE 110 and the base stations 105. The RRCprotocol layer may also be used for the core network 115 support ofradio bearers for the user plane data. At the physical (PHY) layer, thetransport channels may be mapped to physical channels.

The UEs 110 may be dispersed throughout the wireless communicationnetwork 100, and each UE 110 may be stationary and/or mobile. A UE 110may also include or be referred to by those skilled in the art as amobile station, a subscriber station, a mobile unit, a subscriber unit,a wireless unit, a remote unit, a mobile device, a wireless device, awireless communications device, a remote device, a mobile subscriberstation, an access terminal, a mobile terminal, a wireless terminal, aremote terminal, a handset, a user agent, a mobile client, a client, orsome other suitable terminology. A UE 110 may be a cellular phone, asmart phone, a personal digital assistant (PDA), a wireless modem, awireless communication device, a handheld device, a tablet computer, alaptop computer, a cordless phone, a smart watch, a wireless local loop(WLL) station, an entertainment device, a vehicular component, acustomer premises equipment (CPE), or any device capable ofcommunicating in wireless communication network 100. Additionally, a UE110 may be Internet of Things (IoT) and/or machine-to-machine (M2M) typeof device, e.g., a low power, low data rate (relative to a wirelessphone, for example) type of device, that may in some aspects communicateinfrequently with wireless communication network 100 or other UEs 110. AUE 110 may be able to communicate with various types of base stations105 and network equipment including macro gNBs, small cell gNBs, macrogNBs, small cell gNBs, relay base stations, and the like.

A UE 110 may be configured to establish one or more wirelesscommunication links 135 with one or more base stations 105. The wirelesscommunication links 135 shown in wireless communication network 100 maycarry uplink (UL) transmissions from a UE 110 to a base station 105, ordownlink (DL) transmissions, from a base station 105 to a UE 110. Thedownlink transmissions may also be called forward link transmissionswhile the uplink transmissions may also be called reverse linktransmissions. Each wireless communication link 135 may include one ormore carriers, where each carrier may be a signal made up of multiplesub-carriers (e.g., waveform signals of different frequencies) modulatedaccording to the various radio technologies described above. Eachmodulated signal may be sent on a different sub-carrier and may carrycontrol information (e.g., reference signals, control channels, etc.),overhead information, user data, etc. In an aspect, the wirelesscommunication links 135 may transmit bi-directional communications usingfrequency division duplex (FDD) (e.g., using paired spectrum resources)or time division duplex (TDD) operation (e.g., using unpaired spectrumresources). Frame structures may be defined for FDD (e.g., framestructure type 1) and TDD (e.g., frame structure type 2). Moreover, insome aspects, the wireless communication links 135 may represent one ormore broadcast channels.

In some aspects of the wireless communication network 100, the basestations 105 or UEs 110 may include multiple antennas for employingantenna diversity schemes to improve communication quality andreliability between base stations 105 and UEs 110. Additionally oralternatively, base stations 105 or UEs 110 may employ multiple inputmultiple output (MIMO) techniques that may take advantage of multi-pathenvironments to transmit multiple spatial layers carrying the same ordifferent coded data.

The wireless communication network 100 may support operation on multiplecells or carriers, a feature which may be referred to as carrieraggregation (CA) or multi-carrier operation. A carrier may also bereferred to as a component carrier (CC), a layer, a channel, etc. Theterms “carrier,” “component carrier,” “cell,” and “channel” may be usedinterchangeably herein. A UE 110 may be configured with multipledownlink CCs and one or more uplink CCs for carrier aggregation. Carrieraggregation may be used with both FDD and TDD component carriers. Thebase stations 105 and UEs 110 may use spectrum up to Y MHz (e.g., Y=5,10, 15, or 20 MHz) bandwidth per carrier allocated in a carrieraggregation of up to a total of Yx MHz (x=number of component carriers)used for transmission in each direction. The carriers may or may not beadjacent to each other. Allocation of carriers may be asymmetric withrespect to DL and UL (e.g., more or less carriers may be allocated forDL than for UL). The component carriers may include a primary componentcarrier and one or more secondary component carriers. A primarycomponent carrier may be referred to as a primary cell (PCell) and asecondary component carrier may be referred to as a secondary cell(SCell).

The wireless communications network 100 may further include basestations 105 operating according to Wi-Fi technology, e.g., Wi-Fi accesspoints, in communication with UEs 110 operating according to Wi-Fitechnology, e.g., Wi-Fi stations (STAs) via communication links in anunlicensed frequency spectrum (e.g., 5 GHz). When communicating in anunlicensed frequency spectrum, the STAs and AP may perform a clearchannel assessment (CCA) or a listen before talk (LBT) procedure priorto communicating in order to determine whether the channel is available.

Additionally, one or more of the base stations 105 and/or UEs 110 mayoperate according to a NR or 5G technology referred to as millimeterwave (mmW or mmwave) technology. For example, mmW technology includestransmissions in mmW frequencies and/or near mmW frequencies. Extremelyhigh frequency (EHF) is part of the radio frequency (RF) in theelectromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz and awavelength between 1 millimeter and 10 millimeters. Radio waves in thisband may be referred to as a millimeter wave. Near mmW may extend downto a frequency of 3 GHz with a wavelength of 100 millimeters. Forexample, the super high frequency (SHF) band extends between 3 GHz and30 GHz, and may also be referred to as centimeter wave. Communicationsusing the mmW and/or near mmW radio frequency band has extremely highpath loss and a short range. As such, the base stations 105 and/or UEs110 operating according to the mmW technology may utilize beamforming intheir transmissions to compensate for the extremely high path loss andshort range.

Referring to FIGS. 2A and 2B, an example ACK resource allocation 200 forPUCCH formats la includes implicit mapping, and an example LTE ACKresource allocation 201 for PUCCH format 1b includes explicit mappingwith ARI. The gNB 105 may be a carrier aggregated cell with one primarycell (PCell) and one or more secondary cells (Scells).

In such a carrier aggregated configuration, the gNB 105 may use PUCCHformat 210 with implicit mapping to allocate (e.g., assign, identify,etc.) ACK/NACK resources for a PCell and an explicit selection withACK/NACK resource indicator (ARI) 260 to allocate ACK/NACK resources fora SCell. For example, an ACK/NACK resource may be a time/frequencyresource which may identify a frequency, shift, code divisionmultiplexing (CDM), etc. associated with the specific ACK resource. AnACK/NACK resource may be referred to as an “ACK resource” in the presentdisclosure, however, the ACK resource may be used to transmit an ACK ora NACK.

The gNB 105 may transmit PDCCHs 212, 214, 216, and/or 218 which may beassociated with the PCell; and may transmit PDCCHs 262, 264, 266, and/or268 which may be associated with the SCell. For the PCell, gNB 105 mayassign ACK resources using implicit mapping which may include assigningACK resources based on indicating a starting downlink control (DL)channel element resource (CCE) of a resource pool, e.g., resource pool220. For example, PDCCHs 212, 214, 216, and/or 218 may be assigned CCEresources 222, 224, 226, and/or 228, respectively, which may beindicated based on their starting CCE (e.g., a CCE number). The use ofthe starting CCE to identify ACK resources minimizes overhead innotifying the UE 110 about which ACK resources the UE 110 should use fortransmitting an ACK for a specific PDCCH. The implicit mapping may alsoresult in not having to explicitly indicate which ACK resource to use.

For the SCell, for cross-carrier scheduling, gNB 105 may use implicitmapping, as described above in the context of the PCell.

However, for non-cross carrier scheduling, gNB 105 may use PUCCH format260 with explicit mapping based on ARI for assigning ACK resources tothe SCell to avoid collisions (e.g., collisions due to assigning thesame ACK resource for two PUCCHs). For example, for the SCell, the gNB105 may assign ACK resources 272, 276, 274, and/or 278 (from resourcepool 270) for PDCCHs 262, 266, 264, and/or 268, respectively. In oneaspect, the gNB 105 may also include ARI 282 to be transmitted in PDCCH262. For example, the ARI 282 may contain two bits which may includefour possibilities (e.g., 00, 01, 10, 11) for identifying the ACKresources. An example value of 00 for the ARI 282 may identify the ACKresource 272, an example value of 10 for the ARI 282 may identify theACK resource 276, and so on. The use of the ARI 282 for explicitselection of ACK resources may minimize collisions in non-cross carrierscheduling configurations.

FIGS. 3A and 3B illustrate example sub-band dependent mappings 310 and350 according to aspects of the present disclosure.

For example, in NR, multiple DL/UL sub-bands may be configured and theDL sub-bands and the UL sub-bands may have one-to-one mapping or amany-to-one mapping (more than one DL sub-band mapped to one ULsub-band). In one implementation, if DL/UL sub-bands are one-to-onemapped, implicit mapping, described above in reference to FIG. 2, may beused. However, if more than one DL sub-bands are mapped to one ULsub-band, the ACK resources are to be assigned/allocated in a way tominimize/avoid resource collisions. In other words, the ACK resource isgenerally not assigned to multiple PUCCHs of different UEs.

In an aspect, more than one DL sub-bands may be mapped to one ULsub-band. In such a scenario, the sub-band dependent mapping may beperformed in multiple ways. For example, all CCEs in DL sub-bands andall ACK resources in UL sub-bands may be numbered together and sub-bandoffsets may be sent via radio resource control (RRC) configuration orsystem information blocks (SIBS). The implicit mapping, described abovein reference to FIG. 2, may be used. In one more such implementation,CCEs in the DL sub-bands and the ACK resources in the UL sub-bands arenumbered independently. In such a scenario where the CCEs and the ACKresources are numbered independently, one DL sub-band may be mapped toone UL sub-band, and each DL sub-band has an ACK resource offset. TheACK resources may be selected based on the starting CCE and the sub-bandoffset. The sub-band offset may be broadcasted to the UEs via systeminformation blocks (SIBS). In another aspect, resource pools may bebroadcasted via SIBS or via RRC configurations, and ARIs in the PDCCHmay indicate the specific ACK resources to use.

As illustrated in FIG. 3A, four DL sub-bands (312, 314, 316, and 318)are shown and each DL sub-band may transmit multiple PDCCHs. Forexample, in sub-band 312, two PDCCHs, PDCCH1 322 and PDCCH2 323 may betransmitted. On the UE 110 side, two UL sub-bands 330 and 340 are shownand each UL sub-band may have multiple ACK resources. For example, ULsub-band 330 may have ACK resources 332, 334, 336, and/or 338. The linesfrom a DL sub-band to the UL sub-bands show the mapping of multiplePDCCHs (or PDCCH channels) per DL sub-band to multiple ACK resources inthe UL sub-band. For example, PDCCH1 322 and PDCCH2 323 of DL sub-band312 may be mapped to ACK resources 332 and 334 of UL sub-band 330 andPDCCH3 324 and PDCCH4 325 of DL sub-band 314 may be mapped to ACKresources 342 and 344 of UL sub-band 330.

Additionally, as illustrated in FIG. 3B, four DL sub-bands (352, 354,356, and 358) are shown and each DL sub-band may transmit multiplePDCCHs. For example, in sub-band 352, two PDCCHs, PDCCH5 362 and PDCCH6364 may be transmitted. On the UE 110 side, two UL sub-bands 370 and 380are shown and each UL sub-band may have multiple ACK resources. Forexample, UL sub-band 370 may have ACK resources 372, 374, 376, and/or378. The lines from a DL sub-band to the UL sub-bands show the mappingof multiple PDCCHs (or PDCCH channels) per DL sub-band to multiple ACKresources in the UL sub-band. However, the mapping is based on ARIinside PDCCH payload and the mapping may be randomized. For example,PDCCH5 362 and PDCCH6 364 of DL sub-band 352 may be mapped to ACKresources 372 and 378 of UL sub-band 370 and PDCCH7 366 and PDCCH8 368of DL sub-band 356 may be mapped to ACK resources 374 and 376 of ULsub-band 330.

In an implementation, for example, a value of an ARI received in a PDCCHmay be used jointly with implicit mapping for resource allocation withina UE-specific resource set for PUCCH transmissions. In an example, eachUE-specific resource set may include a number of PUCCH resources. Forexample, the number of PUCCH resources in the resource set may be from 8to up to 32. In some cases, the PUCCH resources may be physicalresources in one or more UL sub-bands mapped from more than one DLsub-band, and thus the present aspects operate to avoid collisions. Forinstance, the UE 110 may receive the configuration information from thegNB that identifies the UE-specific resource set (e.g., from 8 to 32resources). Then, the UE 110 may receive the ARI in the PDCCH. In anexample where the ARI has a P-bit value (for example, P may equal 3 or4), the UE 110 may implicitly map a value of the P-bit ARI to a subsetof the UE-specific resources (e.g., a subset of the 4 to 8 PUCCHresources in one or more UL sub-bands) that are to be used to transmitUCI, such as an ACK/NACK. In other words, the UE 110 can map differentvalues of the ARI bits to different subsets of the UE-specific resourceset, and, further, the UE 110 may use implicit mapping to selectspecific resources within the subset identified by the ARI. Thus, theUE-specific resource set is semi-statically configured and ARI bits areused by the UE 110 to perform dynamic resource selection of a subset ofthe UE-specific resources.

In an aspect, if the number of ARI bits is P_ARI, and the UE 110requires more than 2^b_ARI resources for the UCI transmission, then theUE 110 may use the above-noted implicit mapping, and may additionallyreceive an explicit indication of additional UE-specific resources touse. In another example, a 3-bit ARI with up to 8 PUCCH resources perresource set may be implemented. And implicit mapping may be used whenthe number of resources in the resource set is more than 8.

FIGS. 4A and 4B illustrate example cross-slot scheduling configurations.

FIG. 4A illustrates an aggregated DL centric slot schedulingconfiguration 400 with PDCCH scheduling PDSCH transmissions, PDCCHs 411and 413 scheduling transmission of PDSCHs 410 and 420. In such anaggregated DL configuration, for example, two consecutive DL centricslots 410 and 420, different mapping functions with different offsetsmay be used for same-slot scheduling and cross-slot scheduling. In anaspect, ACK/NACKs for PDCCHs 422 and 424 are transmitted in an uplinkshort burst of slot 420 (e.g., cross-slot) and ACK/NACK for PDCCH 426 istransmitted in the uplink short burst of the same slot, slot 420. Asillustrated in FIG. 4A, although PDCCH channels corresponding to 424 and426 are transmitted in the same resource in different slots, they aremapped to different ACK resource in the same ULSB. The mapping caneither be done with different slot-dependent offset combined withimplicit mapping of PDCCH starting CCEs, or with explicit selection ofARI in PDCCH.

FIG. 4B illustrates an aggregated UL centric slot schedulingconfiguration 450 with PDCCH scheduling PDSCH transmissions, PDCCHs 461and 463 scheduling transmission of PDSCHs 460 and 470. In such aconfiguration, for example, with two consecutive aggregated DL centricslots 460 and 470 and two consecutive aggregated UL centric slots 480and 490, multiple PDCCHs, e.g., PDCCHs 464 and 474 may be mapped to asame ACK resource if ACK/NACKs are to be transmitted in long duration ofdifferent slots, e.g., during long slots 480 and 490. In oneimplementation, a slot dependent offset may be added that is subtractedfrom a CCE offset. For example, ACK resource=starting CCE−CCE offset.The slot dependent offset may be communicated to the UE 110 via SIB orRRC configuration. In another implementation, the ARI may be used toexplicitly indicate the ACK resources.

FIG. 5 illustrates an example of an ACK format 500, which may be varied,according to aspects of the present disclosure.

In an aspect, FIG. 5 illustrates a 4 bit ACK 550 for PDSCHs 510, 520,530, and/or 540. In the example, the ACK bits for multiple PDSCHs indifferent slots are transmitted together in the same PUCCH channel,referred to as the HARQ group based multi-bit ACK transmission. In anaspect, a PDSCH may have multiple code blocks (CBs) and one ACK bit maycorrespond to one CB group (CBG) with one or more CBs per CBG. MultipleACK bits may be transmitted for different CBGs in one PDSCH. Therefore,the payload size of ACK channel may be different. Multiple ACK formatsmay be defined for different payload size ranges. The ACK resources fordifferent payload sizes/formats may be different. For example, the ACKresources with a payload of 1 or 2 bits may have one resource pool(e.g., first resource pool), ACK resources with a payload of 2-10 bitsmay have a different resource pool (e.g., second resource pool), and ACKresources with 10+ bits may have another resource pool (e.g., thirdresource pool).

In an aspect, different ACK formats may have different resource pools.For example, gNB 110 may indicate different ACK formats, payload sizes,and/or CBG sizes via downlink control information (DCI) or the UE 110may use certain implicit rules to determine the ACK formats, payloadsizes, and/or CBG sizes. The UE 110, upon determining the ACK formats,may use the implicit mapping or use the ARI indication as describedabove, to select the resource index within the resource pool. In afurther aspect, for HARQ group based multi-bit ACKs, implicit mappingmay be used based on first or last PDCCH in the group. The HARQ grouprange may be signaled by setting K1 values in the PDCCH or byconfiguring a time span in the PDCCH. In one example in FIG. 5, a K1value configured in PDCCH as 4, 3, 2, 1 may result in 4 ACK bitscorresponding to the 4 PDSCH channels to be transmitted together. In anadditional implementation, the ACK payload size may be dynamicallyconfigured. As a result, the number of RBs may be different and/or thenumber of RBs may be derived from ACK payload size.

In an aspect, for example, the UE 110 may select one UCI resource setfrom one or more (up to K=4) configured UCI resource sets based on theUCI payload size, e.g., not including a CRC. A UCI resource set i forUCI payload size may be in the range of {N_(i), . . . , N_(i+1)} bits(i=0, . . . , K−1). In some cases, the value of N may be set for certainvalues of i. For instance, for i equal to 0 or 1, N₀=1 and N₁=2. Assuch, any remaining values of i may corresponding to UE-specificresource sets. For instance, continuing with the above example, for i=2,. . . , K−1, N_(i) may be configured specifically to the UE 110. In anexample, the value of N is in the range of {4, 256} with a granularityof 4 bits. N_(K) may represent a maximum UCI payload size, which may beimplicitly or explicitly derived. In some example, N_(K) may besemi-statically configured in the RRC configuration. Also, in someaspects, for a given UCI payload range, a PUCCH resource set can containresources for short PUCCH and resources for long PUCCH.

Referring to FIG. 6, for example, a method 600 of wireless communicationincluding determining ACK/NACK resources at UE 110 according to theabove-described aspects is disclosed.

For example, at 605, the method 600 includes receiving, from an gNB, aradio resource control (RRC) configuration indicating a UE-specificresource set that is a subset of a gNB resource pool. For instance, inan aspect, the UE 110 and/or modem 140 may execute the communicationscomponent 150 and/or RRC/PDCCH receiving component 152 to receive theRRC configuration from the gNB 105. The RRC configuration may containinformation directing or otherwise linking the UE to a subset of the gNBresource pool. The subset of the gNB resource pool assigned to the UEmay be specific to the UE, thereby avoiding collisions, and the RRCconfiguration may indicate to the UE which resources of the resourcesavailable in the gNB resource pool the UE should use for transmittingACK/NACKs or other UCI information. As such, the UE-specific resourceset may be a semi-statically updated by the RRC configuration.

For example, at 610, the method 600 includes receiving, from an gNB, aphysical downlink control channel (PDCCH) including a correspondingACK/NACK resource configuration. In some cases, the received PDCCH maybe one of one or more PDCCHs each including a corresponding ACK/NACKresource configuration. For instance, in an aspect, the UE 110 and/ormodem 140 may execute the communications component 150 and/or RRC/PDCCHreceiving component 152 to receive one or more PDCCHs from gNB 105 eachincluding a corresponding ACK/NACK resource configuration. As describedabove, each PDCCH may include an ACK/NACK resource configuration whichindicates to the UEs, e.g., UE 110, the ACK/NACK resources from theUE-specific resource set indicated in the RRC configuration, are to beused by the UE 110 for transmitting ACK/NACKs or other UCI in the PUCCH.For instance, in an example, the ACK/NACK resource configurationincludes an ARI having a set of bits, where different values of the setsof bits may be used to indicate different subsets of the UE-specificresources to be used.

Further, at 620, the method 600 includes determining, at the UE, one ormore ACK/NACK resources from the UE-specific resource set for anupcoming PUCCH based, at least in part, on the ACK/NACK resourceconfiguration. For instance, in an aspect, the UE 110 and/or modem 140may execute the communications component 150 and/or ACK/NACK resourcedetermining component 154 to determine one or more ACK/NACK resourcesassociated with the PDCCH. The UE 110 and/or ACK/NACK resourcedetermining component 154 may determine the ACK/NACK resources based atleast in part on the ACK/NACK configuration.

For example, in an aspect where the ACK/NACK configuration includes theARI and the UE-specific resource set is semi-statically configured, theUE 110 uses a value of the ARI bits to perform dynamic resourceselection of a subset of the UE-specific resources. For instance, the UE110 can map different values of the ARI bits to different subsets of theUE-specific resource set. Further, as described above, the UE 110 mayuse implicit mapping to select specific resources within the subsetidentified by the ARI.

In an aspect, as described above, the ACK/NACK configuration that mayimplicitly and/or explicitly indicate which resources from theUE-specific resource set are to be used by the UE 110 in transmittingACK/NACKs.

In an aspect, the UE-specific resource set may include N resources, andthe ARI may be b_ARI-bits, where different values of the b_ARI bitsindicate different subsets of the N resources. If the UE 110 requiresmore than 2^b_ARI resources for the UCI transmission, then the UE 110may use the above-noted implicit mapping, and may additionally receivean explicit indication of additional UE-specific resources to use. Forexample, if N=16, b_ARI bits=3, each ARI value will indicate oneresource subset of the 16 resources. Each resource subset may contain 2resources. An implicit mapping method is used to further select one ofthe two resources in the resource subset. In another example, a 3-bitARI with up to 8 PUCCH resources per resource set may be implemented. Inthis example, one ARI value will select one of the up to 8 resources. Noimplicit mapping is further required.

In some aspects, the implicit mapping method determining the one or moreACK/NACK resources from the UE-specific resource subset is further basedon a location of a control channel element (CCE) carrying the ACK/NACKresource configuration. One example is described above with reference toFIG. 2A.

In some aspects the determination of the ACK/NACK resources to be usedmay be based at least on the DL/UL sub-band mapping function describedin reference to FIGS. 3A and 3B, cross-slot scheduling informationdescribed in reference to FIGS. 4A and 4B, ACK formats described abovein reference to FIG. 5, and/or ARIs.

Optionally, at 630, the method 600 may optionally include transmitting,from the UE, an ACK/NACK for a physical downlink shared channel (PDSCH)on at least one of the one or more ACK/NACK resources determined basedat least in part on the ACK/NACK resource configuration. In someinstance, that PDSCH may be one of one or more PDSCHs associated with arespective PDCCH of one or more PDCCHs that may be received by the UE110. For instance, in an aspect, the UE 110 and/or modem 140 may executethe communications component 150 and/or ACK/NACK transmitting component156 to transmit ACK/NACK for a PDSCH using at least one of thedetermined ACK/NACK resources.

The ACK/NACK resource configuration information transmitted from the gNB105 and/or received at the UE 110 may include any combination of one ormore of downlink(DL)/uplink sub-band mapping information, cross-slotscheduling information, ACK formats, or ACK/NACK resource indicators(ARIs) which are included in the resource configuration of thecorresponding PDCCH.

In some cases, the sub-band mapping information is based on a mapping ofa plurality of downlink sub-bands to one or more uplink sub-bands. In anaspect, the sub-band mapping information is based on an overallnumbering of downlink control channel element (CCE) resources and uplinkACK resources. In an aspect, the sub-band mapping information is basedon an implicit mapping of downlink control channel element (CCE)resources and sub-band dependent offsets.

In an aspect, the cross-slot scheduling information includes differentmapping functions for same-slot scheduling and cross-slot schedulingconfigurations. In an aspect, the cross-slot scheduling information isdetermined by mapping of PDCCHs to a same resource when the ACK/NACKresource configuration indicates an ACK/NACK is to be transmitted in along duration of different slots.

In an aspect, the ARI is a multi-level resource index that includes oneor more sub-band indexes and one or more resource identifiers thatidentify at least one resource corresponding to each sub-band identifiedby the one or more sub-band indexes.

As such, the ARI values included in the PDCCHs may be interpreteddifferently at the UE 110. For example, in one implementation, the ARImay be a multi-level resource index which may be a two-level resourceindex that include a combination of sub-band index and resources withina sub-band. In another example, the ARI may be three-level resourceindex which may include a sub-band index, pay load size (e.g., size ofthe resource pool), and/or a resource index within the resource pool. Inan additional example, the ARI may be a four-level index if theshort/long duration indication is included. Further, in anotherimplementation, the ARI may be defined to index a resource within theentire UL band. In other words, the UE 100 may derive the sub-band basedon the index. Additionally, if mirror hopping or some other hopping(e.g., offset based hopping) is enabled for the PUCCH, the hoppingoperation may be derived based on the resource in the sub-band as thehopping operation may be defined on a per sub-band basis. Furthermore,in another implementation, the ARI values may be configured separatelyfor same-slot and cross-slot scheduling configurations. For example, afirst set of four possible resources indexed by the ARI may be used forthe same-slot scheduling while a second of four possible resourcesindexed by the ARI may be used for the cross-slot scheduling.

In one implementation, the ACK payload size, resource index, etc. may bedynamically changed. For example, the ACK payload may be dynamicallychanged to a 1 bit ACK, CBG based multi-bit ACK, or a HARQ group basedmulti-bit ACK. As a result, the number of RBs may be different based onthe size of the payload, as discussed in greater detail with referenceto FIG. 7. In an additional example, the resource index may bedynamically changed, which may include short/long burst indication,sub-band index/offset, resource pool index, and/or index within thesub-band/resource pool.

Thus, as described above, communications component 150 determinesACK/NACK resources at the UE 110 from a UE-specific resource set andtransmits ACK/NACKs or other UCI to the gNB 110.

Referring to FIG. 7, for example, a method 700 of wireless communicationincluding determining ACK/NACK resources from multiple uplink controlinformation (UCI) resource sets at UE 110 according to theabove-described aspects is disclosed.

For example, at 710, the method 700 includes receiving, from an gNB, aradio resource control (RRC) configuration indicating multipleUE-specific uplink control information (UCI) resource sets that aresubsets of a gNB resource pool. For instance, in an aspect, the UE 110and/or modem 140 may execute the communications component 150 and/orRRC/PDCCH receiving component 152 to receive the RRC configuration fromthe gNB 105. The RRC configuration may contain information directing orotherwise linking the UE to multiple UCI subsets of the gNB resourcepool. The UCI subsets of the gNB resource pool assigned to the UE may bespecific to the UE, e.g., to avoid collisions with other UEtransmissions, and may indicate payload size ranges appropriate for eachof the multiple UE-specific UCI subsets.

Further, at 720, the method 700 includes determining, at the UE, a sizeof a payload for a UCI to be transmitted on a physical uplink controlchannel (PUCCH). For instance, in an aspect, the UE 110 and/or modem 140may execute the communications component 150 and/or ACK/NACK resourcedetermining component 154 to determine the size, or number of bits, of apayload of the UCI the UE 110 intends to transmit with an upcomingPUCCH.

Optionally, at 730, the method 700 may include receiving, from the gNB,a PDCCH including a corresponding ACK/NACK resource configuration. Forinstance, in an aspect, the UE 110 and/or modem 140 may execute thecommunications component 150 and/or RRC/PDCCH receiving component 152 toreceive one or more PDCCHs from gNB 105. Each PDCCH may include anACK/NACK resource configuration, which indicates to the UEs, e.g., UE110, the ACK/NACK resources from the UE-specific UCI resource setsindicated in the RRC configuration, are to be used by the UE 110 fortransmitting ACK/NACKs in the PUCCH. For example, in one aspect, theACK/NACK resource configuration may be an ARI. In some aspects, theACK/NACK resource configuration includes an acknowledgement resourceindicator (ARI), and the UCI comprises an acknowledgement ACK or a NACK.

Further, at 740, the method 700 includes determining, at the UE, aselected UE-specific UCI resource set from the multiple UE-specificresource sets for transmitting the UCI on the PUCCH based, at least inpart, on the size of the payload of the UCI. For instance, in an aspect,the UE 110 and/or modem 140 may execute the communications component 150and/or ACK/NACK resource determining component 154 to determine one ormore ACK/NACK resources from one of the multiple UCI resource setsbased, at least in part, on the determined payload size. Thecommunications component 150 and/or ACK/NACK resource determiningcomponent 154 may identify payload ranges associated with each of themultiple UCI resource sets. For example, but not limited hereto, a firstresource set may be used for payloads ranging in size from 1 bits to 2bits, while a second resource set may be used with payloads ranging insize from 3-12 bits. The communications component 150 and/or ACK/NACKresource determining component 154 may identify which of the payloadsize ranges overlap with the determined payload size. That is, the UE110 may determine whether the determined payload size falls within anyof the identified payload size ranges. The UE 110 may select one of themultiple UCI resource sets having a payload size range within which thedetermined payload size is included. In a further example, but notlimited hereto, a determined payload size of 8 bits could be transmittedwith resources from either of the aforementioned resource sets, but apayload size of 4 bits could only be transmitted with resources from thefirst resource set.

In some aspects, determining the selected UE-specific UCI resource setmay further include selecting one or more resources within the selectedUE-specific UCI resource set based on implicit and/or explicit mapping.For example, such aspects may include receiving an acknowledgementresource indicator (ARI), and mapping to the one or more resourceswithin the selected UE-specific UCI resource set based on a value of theARI. As such, some aspects may include receiving an ARI and selectingone or more resources within the selected UE-specific UCI resource setbased on the ARI.

In some aspects, the ARI includes a resource index, and thus determiningthe selected UE-specific UCI resource set may further include selectinga sub-band associated with the one or more resources based on theresource index. For example,

In some aspects, in response to receiving the ARI, determining theselected UE-specific UCI resource set may further include selecting,based on the ARI, a first group of one or more resources within theselected UE-specific UCI resource set for same-slot scheduling or asecond group of one or more resources within the selected UE-specificUCI resource set for cross-slot scheduling. In some aspects, determiningthe one or more ACK/NACK resources from the UE-specific resource set isbased, at least in part, on cross-slot scheduling information and PDCCHsof different slots have ARIs of equal value.

Optionally, at 750, the method 700 may include transmitting the UCI viathe selected UE-specific UCI resource set on the PUCCH. For instance, inan aspect, the UE 110 and/or modem 140 may execute the communicationscomponent 150 and/or ACK/NACK transmitting component 156 to transmit theUCI, e.g., an ACK/NACK for a PDSCH, using the selected UE-specific UCIresource set on the PUCCH.

In aspects implementing optional block 730, the specific ACK/NACKresources to be used within each of the multiple UCI resource sets maybe determined based, at least in part, on the ACK/NACK configurationreceived within the PDCCH. The UE 110 and/or ACK/NACK resourcedetermining component 154 may determine the ACK/NACK resources based atleast in part on the ACK/NACK configuration. The ACK/NACK configurationmay include an acknowledgement resource indicator (ARI) specificallyindicating which exact resources from a selected UCI resource set (e.g.,a selected subset of the multiple sets of resources within theUE-specific resource set) are to be used by the UE 110 in transmittingACK/NACKs. Thus, once the UE 110 has selected one of the multiple UCIresource sets based on the payload size, the UE 110 may then use theACK/NACK configuration to select specific ACK/NACK resources of the UCIresource set for use in transmitting the ACK/NACK within the PUCCH.

In a further additional example, payload size may be different whencombined with other UCI. For example, when combined with a channelquality indicator (CQI), payload size may be different as the CQI mayhave different beam related information. Additionally, the ACK payloadsize may be different. For instance, if a UE is supposed to transmit 10bits of ACK, but after combining with the CQI, the UE may be able totransmit only 3 ACK bits. In such scenarios, ACK bundling may be used tomerge the ACK bit, or a sub-set of bits may be transmitted and theremaining ACK bits may be transmitted later. Further, the startingresource block and the number of RBs and PUCCH formats (payload sizedependent) may be explicitly configured.

Referring to FIG. 8, for example, a method 800 of wireless communicationincluding determining ACK/NACK resources at gNB 105 according to theabove-described aspects is disclosed.

For example, at 805, the method 800 includes transmitting, to a UE, aradio resource control (RRC) configuration indicating a UE-specificresource set that is a subset of a gNB resource pool. For instance, inan aspect, the gNB 105 and/or modem 180 may execute the communicationscomponent 190 to transmit the RRC configuration to UE 110. The RRCconfiguration may contain information directing or otherwise linking theUE to a subset of the gNB resource pool. The subset of the gNB resourcepool assigned to the UE may be specific to the UE. The gNB 105 mayselect a resource set to assign to the UE using a variety of techniques.For example, in an implementation, the gNB may select a resource set byidentifying available resources at random from the gNB resource pool.Alternatively, in an implementation the gNB may select resources fromthe next available block of resources in the gNB resource pool. In afurther implementation, the gNB may select contiguous blocks ofresources from the gNB resource pool. The gNB may assign the resourcesto the UEs such that the probability of any of the UEs being assigned tothe same resource is small.

For example, there may be a total 200 PUCCH resources and a total of 100UEs with each UE having 16 resources in its resource set. The gNB mayrandomly choose 16 out of 200 PUCCH resources for each UE (with some ofthe 16 being short PUCCH resource and the rest for long PUCCH) as theresource set to be identified in the in RRC configure. In a particularslot, if the 10 out of 100 UE need to transmit PUCCH, gNB may select oneof the 16 resources from these UE's resource set to that the probabilityof any of the two UEs using the same resource is minimized.

For example, at 810, the method 800 includes transmitting, to the UE, aphysical downlink control channel (PDCCH) including a correspondingACK/NACK resource configuration. In some cases, the transmitted PDCCHmay be one of one or more PDCCHs each including a corresponding ACK/NACKresource configuration. For instance, in an aspect, the gNB 105 and/ormodem 180 may execute the communications component 190 and/or PDCCHtransmitting component 192 to transmit one or more PDCCHs from gNB 105each including a corresponding ACK/NACK resource configuration. Asdescribed above, each PDCCH may include an ACK/NACK resourceconfiguration which indicates to the UEs, e.g., UE 110, the ACK/NACKresources from the UE-specific resource set indicated in the RRCconfiguration, are to be used by the UE 110 for transmitting ACK/NACKsor other UCI in the PUCCH. The ACK/NACK resource configuration mayinclude an acknowledgement resource indicator (ARI). Further, the ARImay be a multi-level resource index that includes one or more sub-bandindexes and one or more resource identifiers that identify at least oneresource corresponding to each sub-band identified by the one or moresub-band indexes. Moreover, one or more of the PDCCHs may identify oneor more resource elements associated with a physical downlink sharedchannel (PDSCH) to be used to send user data to the UE 110.

For example, at 815, the method 800 includes transmitting, to the UE,user data on a physical downlink shared channel (PDSCH). For instance,in an aspect, the gNB 105 and/or modem 180 may execute thecommunications component 190 to transmit user data from gNB 105 to UE110 on one or more resource elements of the PDSCH as identified incontrol information, such as the PCCCH.

For example, at 820, the method 800 may include receiving, from the UE,an ACK/NACK for the user data transmitted on the PDSCH on at least oneACK/NACK resource determined by the UE based at least in part on theACK/NACK resource configuration. For instance, in an aspect, the gNB 105and/or modem 180 may execute the communications component 190 and/orACK/NACK receiving component 194 to receive an ACK/NACK from UE 110. ThegNB 104 may receive an ACK/NACK for user data on the PDSCH transmittedby the gNB 105 to confirm whether or not the UE 110 has properlyreceived the signal, e.g., the user data.

Referring to FIG. 9, for example, a method 900 of wireless communicationincluding determining ACK/NACK resources from multiple uplink controlinformation (UCI) resource sets at gNB 105 according to theabove-described aspects is disclosed.

For example, at 910, the method 900 includes transmitting, to a UE, aradio resource control (RRC) configuration indicating multipleUE-specific uplink control information (UCI) resource sets that aresubsets of a gNB resource pool. For instance, in an aspect, the gNB 105and/or modem 180 may execute the communications component 180 totransmit the RRC configuration from the gNB 105 to the UE 110. The RRCconfiguration may contain information directing or otherwise linking theUE to multiple UCI subsets of the gNB resource pool. The UCI subsets ofthe gNB resource pool assigned to the UE may be specific to the UE,e.g., to avoid collisions with other UE transmissions, and may indicatepayload size ranges appropriate for each of the multiple UE-specific UCIsubsets. In some implementations the gNB 105 may select the resourcesets for assignment to the UE based on random selection, selection ofcontiguous resource blocks, and/or selection of the next availableresource blocks.

Optionally, for example, at 920, the method 900 may includetransmitting, to the UE, a PDCCH including a corresponding ACK/NACKresource configuration. For instance, in an aspect, the gNB 105 and/ormodem 180 may execute the communications component 190 and/or PDCCHtransmitting component 192 to transmit one or more PDCCHs from gNB 105to UE 110. Each PDCCH may include an ACK/NACK resource configuration,which indicates to the UEs, e.g., UE 110, the ACK/NACK resources fromthe UE-specific UCI resource sets indicated in the RRC configuration,are to be used by the UE 110 for transmitting ACK/NACKs in the PUCCH.Further, in some aspects, the PDCCH includes one of a plurality ofdifferent format types, wherein each of the plurality of format typescorresponds to a different subset of the multiple UE-specific resourcesets.

For example, at 930, the method 900 may include receiving a UCI in aUE-specific UCI resource set selected by the UE from the multipleUE-specific UCI resource sets based on a payload size of the UCI, on aPUCCH. For instance, in an aspect, the gNB 105 and/or modem 180 mayexecute the communications component 100 and/or ACK/NACK receivingcomponent 194 to receive the UCI, e.g., an ACK/NACK for a PDSCH, usingthe selected UE-specific UCI resource set on the PUCCH. In someimplementations, the UE-specific resource set may be selected by the UE110 based on a payload size of the UCI and/or based on the transmittedACK/NACK resource configuration.

Referring to FIG. 10, one example of an implementation of a UE 110 mayinclude a variety of components, some of which have already beendescribed above, including components such as one or more processors1012, memory 1016 and transceiver 1002 in communication via one or morebuses 1044, which may operate in conjunction with the modem 140 andcommunications component 150 to determine ACK/NACK resources at UE 110.Further, the one or more processors 1012, modem 140, memory 1016,transceiver 1002, RF front end 1088 and one or more antennas 1065, maybe configured to support voice and/or data calls (simultaneously ornon-simultaneously) in one or more radio access technologies.

In an aspect, the one or more processors 1012 can include a modem 140that uses one or more modem processors. The various functions related tocommunications component 150 may be included in modem 140 and/orprocessors 1012 and, in an aspect, can be executed by a singleprocessor, while in other aspects, different ones of the functions maybe executed by a combination of two or more different processors. Forexample, in an aspect, the one or more processors 1012 may include anyone or any combination of a modem processor, or a baseband processor, ora digital signal processor, or a transmit processor, or a receiverprocessor, or a transceiver processor associated with the transceiver1002. In other aspects, some of the features of the one or moreprocessors 1012 and/or modem 140 associated with the communicationscomponent 150 may be performed by the transceiver 1002.

Also, the memory 1016 may be configured to store data used herein and/orlocal versions of applications 1075 or communications component 150and/or one or more of its subcomponents being executed by at least oneprocessor 1012. The memory 1016 can include any type ofcomputer-readable medium usable by a computer or at least one processor1012, such as random access memory (RAM), read only memory (ROM), tapes,magnetic discs, optical discs, volatile memory, non-volatile memory, andany combination thereof. In an aspect, for example, the memory 1016 maybe a non-transitory computer-readable storage medium that stores one ormore computer-executable codes defining communications component 150and/or one or more of its subcomponents, and/or data associatedtherewith, when the UE 110 is operating at least one processor 1012 toexecute the communications component 150 and/or one or more of itssubcomponents.

The transceiver 1002 may include at least one receiver 1006 and at leastone transmitter 1008. The receiver 1006 may include hardware, firmware,and/or software code executable by a processor for receiving data, thecode comprising instructions and being stored in a memory (e.g.,computer-readable medium). The receiver 1006 may be, for example, aradio frequency (RF) receiver. In an aspect, the receiver 1006 mayreceive signals transmitted by at least one base station 105.Additionally, the receiver 1006 may process such received signals, andalso may obtain measurements of the signals, such as, but not limitedto, Ec/Io, SNR, RSRP, RSSI, etc. The transmitter 1008 may includehardware, firmware, and/or software code executable by a processor fortransmitting data, the code comprising instructions and being stored ina memory (e.g., computer-readable medium). A suitable example of thetransmitter 808 may include, but is not limited to, a RF transmitter.

Moreover, in an aspect, the UE 110 may include a RF front end 1088,which may operate in communication with one or more antennas 1065 andtransceiver 802 for receiving and transmitting radio transmissions, forexample, wireless communications transmitted by at least one basestation 105 or wireless transmissions transmitted by the UE 110. The RFfront end 1088 may be communicatively coupled with one or more antennas1065 and can include one or more low-noise amplifiers (LNAs) 1090, oneor more switches 1092, one or more power amplifiers (PAs) 1098, and oneor more filters 1096 for transmitting and receiving RF signals.

In an aspect, the LNA 1090 can amplify a received signal at a desiredoutput level. In an aspect, each LNA 1090 may have a specified minimumand maximum gain values. In an aspect, the RF front end 1088 may use oneor more switches 1092 to select a particular LNA 1090 and its specifiedgain value based on a desired gain value for a particular application.

Further, for example, one or more PA(s) 1098 may be used by the RF frontend 1088 to amplify a signal for an RF output at a desired output powerlevel. In an aspect, each PA 1098 may have specified minimum and maximumgain values. In an aspect, the RF front end 1088 may use one or moreswitches 1092 to select a particular PA 1098 and its specified gainvalue based on a desired gain value for a particular application.

Also, for example, one or more filters 1096 can be used by the RF frontend 1088 to filter a received signal to obtain an input RF signal.Similarly, in an aspect, for example, a respective filter 1096 can beused to filter an output from a respective PA 1098 to produce an outputsignal for transmission. In an aspect, each filter 1096 can be connectedto a specific LNA 1090 and/or PA 1098. In an aspect, the RF front end888 can use one or more switches 1092 to select a transmit or receivepath using a specified filter 1096, LNA 1090, and/or PA 1098, based on aconfiguration as specified by the transceiver 1002 and/or processor1012.

As such, the transceiver 1002 may be configured to transmit and receivewireless signals through one or more antennas 1065 via RF front end1088. In an aspect, the transceiver 1002 may be tuned to operate atspecified frequencies such that the UE 110 can communicate with, forexample, one or more cells associated with one or more base stations105. In an aspect, for example, the modem 140 can configure thetransceiver 1002 to operate at a specified frequency and power levelbased on the configuration of the UE 110 and communication protocol usedby the modem 140.

In an aspect, the modem 140 can be a multiband-multimode modem, whichcan process digital data and communicate with the transceiver 1002 suchthat the digital data is sent and received using the transceiver 1002.In an aspect, the modem 140 can be multiband and be configured tosupport multiple frequency bands for a specific communications protocol.In an aspect, the modem 140 can be multimode and be configured tosupport multiple operating networks and communications protocols. In anaspect, the modem 140 can control one or more components of the UE 110(e.g., RF front end 1088, transceiver 1002) to enable transmissionand/or reception of signals from the network based on a specified modemconfiguration. In an aspect, the modem configuration can be based on themode of the modem and the frequency band in use. In another aspect, themodem configuration can be based on base station information associatedwith the UE 110 as provided by the network during cell selection and/orcell reselection.

Referring to FIG. 11, one example of an implementation of base station105 may include a variety of components, which have already beendescribed above in detail, including components such as one or moreprocessors 1112 and memory 1116 and transceiver 1102 in communicationvia one or more buses 1144, which may operate in conjunction with modem180 and communications component 1110 to enable one or more of thefunctions described herein.

The transceiver 1102, receiver 1106, transmitter 1108, one or moreprocessors 1112, memory 1116, applications 1175, buses 1144, RF frontend 1188, LNAs 11110, switches 11112, filters 11116, PAs 11118, and oneor more antennas 1165 may be the same as or similar to the correspondingcomponents of UE 110, as described above, but configured or otherwiseprogrammed for base station operations as opposed to UE operations.

The above detailed description set forth above in connection with theappended drawings describes examples and does not represent the onlyexamples that may be implemented or that are within the scope of theclaims. The term “example,” when used in this description, means“serving as an example, instance, or illustration,” and not “preferred”or “advantageous over other examples.” The detailed description includesspecific details for the purpose of providing an understanding of thedescribed techniques. These techniques, however, may be practicedwithout these specific details. In some instances, well-known structuresand apparatuses are shown in block diagram form in order to avoidobscuring the concepts of the described examples.

Information and signals may be represented using any of a variety ofdifferent technologies and techniques. For example, data, instructions,commands, information, signals, bits, symbols, and chips that may bereferenced throughout the above description may be represented byvoltages, currents, electromagnetic waves, magnetic fields or particles,optical fields or particles, computer-executable code or instructionsstored on a computer-readable medium, or any combination thereof.

The various illustrative blocks and components described in connectionwith the disclosure herein may be implemented or performed with aspecially-programmed device, such as but not limited to a processor, adigital signal processor (DSP), an ASIC, a FPGA or other programmablelogic device, a discrete gate or transistor logic, a discrete hardwarecomponent, or any combination thereof designed to perform the functionsdescribed herein. A specially-programmed processor may be amicroprocessor, but in the alternative, the processor may be anyconventional processor, controller, microcontroller, or state machine. Aspecially-programmed processor may also be implemented as a combinationof computing devices, e.g., a combination of a DSP and a microprocessor,multiple microprocessors, one or more microprocessors in conjunctionwith a DSP core, or any other such configuration.

The functions described herein may be implemented in hardware, softwareexecuted by a processor, firmware, or any combination thereof. Ifimplemented in software executed by a processor, the functions may bestored on or transmitted over as one or more instructions or code on anon-transitory computer-readable medium. Other examples andimplementations are within the scope and spirit of the disclosure andappended claims. For example, due to the nature of software, functionsdescribed above can be implemented using software executed by aspecially programmed processor, hardware, firmware, hardwiring, orcombinations of any of these. Features implementing functions may alsobe physically located at various positions, including being distributedsuch that portions of functions are implemented at different physicallocations. Also, as used herein, including in the claims, “or” as usedin a list of items prefaced by “at least one of” indicates a disjunctivelist such that, for example, a list of “at least one of A, B, or C”means A or B or C or AB or AC or BC or ABC (i.e., A and B and C).

Computer-readable media includes both computer storage media andcommunication media including any medium that facilitates transfer of acomputer program from one place to another. A storage medium may be anyavailable medium that can be accessed by a general purpose or specialpurpose computer. By way of example, and not limitation,computer-readable media can comprise RAM, ROM, EEPROM, CD-ROM or otheroptical disk storage, magnetic disk storage or other magnetic storagedevices, or any other medium that can be used to carry or store desiredprogram code means in the form of instructions or data structures andthat can be accessed by a general-purpose or special-purpose computer,or a general-purpose or special-purpose processor. Also, any connectionis properly termed a computer-readable medium. For example, if thesoftware is transmitted from a website, server, or other remote sourceusing a coaxial cable, fiber optic cable, twisted pair, digitalsubscriber line (DSL), or wireless technologies such as infrared, radio,and microwave, then the coaxial cable, fiber optic cable, twisted pair,DSL, or wireless technologies such as infrared, radio, and microwave areincluded in the definition of medium. Disk and disc, as used herein,include compact disc (CD), laser disc, optical disc, digital versatiledisc (DVD), floppy disk and Blu-ray disc where disks usually reproducedata magnetically, while discs reproduce data optically with lasers.Combinations of the above are also included within the scope ofcomputer-readable media.

The previous description of the disclosure is provided to enable aperson skilled in the art to make or use the disclosure. Variousmodifications to the disclosure will be readily apparent to thoseskilled in the art, and the common principles defined herein may beapplied to other variations without departing from the spirit or scopeof the disclosure. Furthermore, although elements of the describedaspects and/or embodiments may be described or claimed in the singular,the plural is contemplated unless limitation to the singular isexplicitly stated. Additionally, all or a portion of any aspect and/orembodiment may be utilized with all or a portion of any other aspectand/or embodiment, unless stated otherwise. Thus, the disclosure is notto be limited to the examples and designs described herein but is to beaccorded the widest scope consistent with the principles and novelfeatures disclosed herein.

What is claimed is:
 1. A method of wireless communications at a userequipment (UE), comprising: receiving, from a base station, a radioresource control (RRC) configuration indicating a UE-specific resourceset; receiving, from the base station, a physical downlink controlchannel (PDCCH) including a correspondingacknowledgement/non-acknowledgement (ACK/NACK) resource configuration;determining, at the UE, one or more ACK/NACK resources from theUE-specific resource set for an upcoming physical uplink control channel(PUCCH) based, at least in part, on the ACK/NACK resource configuration;and transmitting, from the UE to the base station, an ACK/NACK for aphysical downlink shared channel (PDSCH) on at least one of the one ormore ACK/NACK resources determined based at least in part on theACK/NACK resource configuration.
 2. The method of claim 1, wherein theone or more ACK/NACK resources is used to transmit a combined UCI thatincludes at least the ACK/NACK and another type of UCI different fromthe ACK/NACK.
 3. The method of claim 1, wherein the ACK/NACK allows thebase station to verify the UE received the RRC configuration and thePDCCH.
 4. The method of claim 1, wherein determining the one or moreACK/NACK resources from the UE-specific resource set is further based,at least in part, on at least one of sub-band mapping information,cross-slot scheduling information, or a format of the ACK/NACK resourceconfiguration.
 5. The method of claim 4, wherein the sub-band mappinginformation is based on a mapping of a plurality of downlink sub-bandsto one or more uplink sub-bands.
 6. The method of claim 4, wherein thesub-band mapping information is based on an overall numbering ofdownlink control channel element (CCE) resources and uplink ACKresources.
 7. The method of claim 4, wherein the sub-band mappinginformation is based on an implicit mapping of downlink control channelelement (CCE) resources and sub-band dependent offsets.
 8. The method ofclaim 4, wherein the cross-slot scheduling information includesdifferent mapping functions for same-slot scheduling and cross-slotscheduling configurations.
 9. The method of claim 4, wherein thecross-slot scheduling information is determined by: mapping a pluralityof PDCCHs to a same resource when the ACK/NACK resource configurationindicates an ACK/NACK is to be transmitted in a long duration ofdifferent slots.
 10. The method of claim 1, wherein the ACK/NACKresource configuration includes a resource indicator (RI).
 11. Themethod of claim 10, wherein determining, at the UE, the one or moreACK/NACK resources from the UE-specific resource set is further based onexplicit mapping of some downlink control information (DCI) bits otherthan RI bits.
 12. The method of claim 10, wherein the RI is amulti-level resource index that includes one or more sub-band indexesand one or more resource identifiers that identify at least one resourcecorresponding to each sub-band identified by the one or more sub-bandindexes.
 13. The method of claim 10, wherein determining, at the UE, theone or more ACK/NACK resources from the UE-specific resource set isfurther based on implicit mapping.
 14. The method of claim 3, whereinthe implicit mapping is based on a location of a control channel element(CCE) carrying the ACK/NACK resource configuration.
 15. The method ofclaim 3, wherein determining, at the UE, the one or more ACK/NACKresources from the UE-specific resource set is based on implicit mappingwhen a number of resources in the UE-specific resource set is more than2^b_RI, where b_RI is a number of RI bits.
 16. A user equipment (UE),comprising: a transceiver; a memory; and a processor coupled with thememory and the transceiver and configured to: receive, from a basestation, a radio resource control (RRC) configuration indicating aUE-specific resource set; receive, from the base station, a physicaldownlink control channel (PDCCH) including a correspondingacknowledgement/non-acknowledgement (ACK/NACK) resource configuration;determine one or more ACK/NACK resources from the UE-specific resourceset for an upcoming physical uplink control channel (PUCCH) based, atleast in part, on the ACK/NACK resource configuration; and transmit, tothe base station an ACK/NACK for a physical downlink shared channel(PDSCH) one at least one of the one or more ACK/NACK resourcesdetermined based at least in part on the ACK/NACK resourceconfiguration.
 17. The UE of claim 16, wherein the one or more ACK/NACKresources is used to transmit a combined UCI that includes at least theACK/NACK and another type of UCI different from the ACK/NACK.
 18. Themethod of claim 16, wherein the ACK/NACK allows the base station toverify the UE received the RRC configuration and the PDCCH.
 19. The UEof claim 16, wherein the processor is further configured to determinethe one or more ACK/NACK resources from the UE-specific resource setbased, at least in part, on at least one of sub-band mappinginformation, cross-slot scheduling information, or a format of theACK/NACK resource configuration.
 20. The UE of claim 19, wherein thesub-band mapping information is based on a mapping of a plurality ofdownlink sub-bands to one or more uplink sub-bands.
 21. The UE of claim19, wherein the sub-band mapping information is based on an overallnumbering of downlink control channel element (CCE) resources and uplinkACK resources.
 22. The UE of claim 19, wherein the sub-band mappinginformation is based on an implicit mapping of downlink control channelelement (CCE) resources and sub-band dependent offsets.
 23. The UE ofclaim 19, wherein the cross-slot scheduling information includesdifferent mapping functions for same-slot scheduling and cross-slotscheduling configurations.
 24. The UE of claim 19, wherein the processoris further configured to determine the cross-slot scheduling informationby: mapping a plurality of PDCCHs to a same resource when the ACK/NACKresource configuration indicates an ACK/NACK is to be transmitted in along duration of different slots.
 25. The UE of claim 16, wherein theACK/NACK resource configuration includes a resource indicator (RI). 26.The UE of claim 25, wherein the processor is further configured todetermine the one or more ACK/NACK resources from the UE-specificresource set further based on explicit mapping of some downlink controlinformation (DCI) bits other than RI bits.
 27. The UE of claim 25,wherein the RI is a multi-level resource index that includes one or moresub-band indexes and one or more resource identifiers that identify atleast one resource corresponding to each sub-band identified by the oneor more sub-band indexes.
 28. The UE of claim 25, wherein the processoris further configured to determine the one or more ACK/NACK resourcesfrom the UE-specific resource set further based on implicit mapping. 29.The UE of claim 28, wherein the implicit mapping is based on a locationof a control channel element (CCE) carrying the ACK/NACK resourceconfiguration.
 30. The UE of claim 28, wherein the processor is furtherconfigured to: determine the one or more ACK/NACK resources from theUE-specific resource set is based on implicit mapping when a number ofresources in the UE-specific resource set is more than 2^b_RI, whereb_RI is a number of RI bits.
 31. A user equipment (UE) comprising: meansfor receiving, from a base station, a radio resource control (RRC)configuration indicating a UE-specific resource set; means forreceiving, from the base station, a physical downlink control channel(PDCCH) including a corresponding acknowledgement/non-acknowledgement(ACK/NACK) resource configuration; means for determining one or moreACK/NACK resources from the UE-specific resource set for an upcomingphysical uplink control channel (PUCCH) based, at least in part, on theACK/NACK resource configuration; and means for transmitting, to the basestation, an ACK/NACK for a physical downlink shared channel (PDSCH) onat least one of the one or more ACK/NACK resources determined based atleast in part on the ACK/NACK resource configuration.
 32. The UE ofclaim 31, wherein the ACK/NACK resource configuration includes aresource indicator (RI).
 33. The UE of claim 31, wherein the one or moreACK/NACK resources is used to transmit a combined UCI that includes atleast the ACK/NACK and another type of UCI different from the ACK/NACK.34. The method of claim 31, wherein the ACK/NACK allows the base stationto verify the UE received the RRC configuration and the PDCCH.
 35. Anon-transitory computer readable medium of a user equipment (UE) havingprocessor-executable program code stored thereon, comprising: code forreceiving, from a base station, a radio resource control (RRC)configuration indicating a UE-specific resource set; code for receiving,from the base station, a physical downlink control channel (PDCCH)including a corresponding acknowledgement/non-acknowledgement (ACK/NACK)resource configuration; code for determining one or more ACK/NACKresources from the UE-specific resource set for an upcoming physicaluplink control channel (PUCCH) based, at least in part, on the ACK/NACKresource configuration; and code for transmitting, to the base station,an ACK/NACK for a physical downlink shared channel (PDSCH) on at leastone of the one or more ACK/NACK resources determined based at least inpart on the ACK/NACK resource configuration.
 36. The non-transitorycomputer readable medium of claim 35, wherein the ACK/NACK resourceconfiguration includes a resource indicator (RI).
 37. The non-transitorycomputer readable medium of claim 35, wherein the one or more ACK/NACKresources is used to transmit a combined UCI that includes at least theACK/NACK and another type of UCI different from the ACK/NACK.
 38. Thenon-transitory computer readable medium of claim 35, wherein theACK/NACK allows the base station to verify the UE received the RRCconfiguration and the PDCCH.
 39. A method of wireless communication at abase station, comprising: transmitting, to a UE, a radio resourcecontrol (RRC) configuration indicating a UE-specific resource set;transmitting, to the UE, a physical downlink control channel (PDCCH)including a corresponding acknowledgement/non-acknowledgement (ACK/NACK)resource configuration; transmitting, to the UE, user data on a physicaldownlink shared channel (PDSCH); receiving, from the UE, an ACK/NACK forthe user data transmitted on the PDSCH on at least one ACK/NACK resourcefrom the UE-specific resource set determined, by the UE, based at leastin part on the ACK/NACK resource configuration; and verifying, by thebase station, the UE received the user data based on the ACK/NACK. 40.The method of claim 39, wherein the ACK/NACK resource configurationincludes a resource indicator (RI).
 41. The method of claim 40, whereinthe RI is a multi-level resource index that includes one or moresub-band indexes and one or more resource identifiers that identify atleast one resource corresponding to each sub-band identified by the oneor more sub-band indexes.
 42. A base station, comprising: a transceiver;a memory; and a processor coupled with the memory and the transceiverand configured to: transmit, to a UE, a radio resource control (RRC)configuration indicating a UE-specific resource set; transmit, to theUE, a physical downlink control channel (PDCCH) including acorresponding acknowledgement/non-acknowledgement (ACK/NACK) resourceconfiguration; transmit, to the UE, user data on a physical downlinkshared channel (PDSCH); receive, from the UE, an ACK/NACK for the userdata transmitted on the PDSCH on at least one ACK/NACK resource from theUE-specific resource set determined, by the UE, based at least in parton the ACK/NACK resource configuration; and verify, by the processor,the UE received the user data based on the ACK/NACK.
 43. The basestation of claim 42, wherein the ACK/NACK resource configurationincludes a resource indicator (RI).
 44. The base station of claim 43,wherein the RI is a multi-level resource index that includes one or moresub-band indexes and one or more resource identifiers that identify atleast one resource corresponding to each sub-band identified by the oneor more sub-band indexes.
 45. A non-transitory computer readable mediumhaving processor-executable program code stored thereon, comprising:code executable to transmit, to a UE, a radio resource control (RRC)configuration indicating a UE-specific resource set; code executable totransmit, to the UE, a physical downlink control channel (PDCCH)including a corresponding acknowledgement/non-acknowledgement (ACK/NACK)resource configuration; code executable to transmit, to the UE, userdata on a physical downlink shared channel (PDSCH); code executable toreceive, from the UE, an ACK/NACK for the user data transmitted on thePDSCH on at least one ACK/NACK resource from the UE-specific resourceset determined, by the UE, based at least in part on the ACK/NACKresource configuration; and code executable to verify, by a basestation, the UE received the user data based on the ACK/NACK.
 46. A basestation, comprising: means for transmitting, to a UE, a radio resourcecontrol (RRC) configuration indicating a UE-specific resource set; meansfor transmitting, to the UE, a physical downlink control channel (PDCCH)including a corresponding acknowledgement/non-acknowledgement (ACK/NACK)resource configuration; means for transmitting, to the UE, user data ona physical downlink shared channel (PDSCH); means for receiving, fromthe UE, an ACK/NACK for the user data transmitted on the PDSCH on atleast one ACK/NACK resource from the UE-specific resource setdetermined, by the UE, based at least in part on the ACK/NACK resourceconfiguration; and means for verifying, by the base station, the UEreceived the user data based on the ACK/NACK.